dev - #193

Walkthrough

Two GitHub Actions workflows are modified to introduce a new version propagation mechanism. The release workflow now outputs a version determined by the release script, switches its trigger to tagged pushes on main, and passes this version to the docker workflow which uses it for image tagging instead of Git references.

Changes

Sequence Diagram

sequenceDiagram
    participant GitHub as GitHub (Push Event)
    participant RW as release.yml
    participant RS as Release Script
    participant DW as docker.yml
    participant Registry as Docker Registry

    GitHub->>RW: Tag push to main
    RW->>RS: Execute with --release-version
    RS->>RS: Determine VERSION
    RS->>RW: Output version to GITHUB_OUTPUT
    RW->>RW: Expose version in outputs
    RW->>DW: Call publish-docker with version input
    DW->>DW: Build image tag: image_name:version-ARCH
    DW->>Registry: Push image with version tag

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

Possibly related PRs

• dev #157: Modifies release workflow step outputs and downstream references, aligning with the version output mechanism changes.
• dev #178: Changes the release workflow trigger configuration from PR-based to event-based, directly related to the new tag-based push trigger.
• dev #151: Modifies release and tag handling in GitHub Actions workflows, including version/tag naming conventions used in Docker image tagging.

Poem

🐰 A version hops through workflows so bright,
From release script to Docker's delight,
Through outputs it flows, with each tagged push,
Building images—no Git reference rush!
Version control's dance, clean and precise. ✨

❌ Failed checks (1 inconclusive)

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}